Motivation and Context

This simplifies the logic of the ConfigMap Watcher functionality that updates CR when the CR templates in ConfigMaps change. The previously applied input fields are now stored within the CRs itself and are re-applied upon update.

This allows for the propagation of MinIO credentials upon update.

PR Checklist

Please check if your PR fulfills the following requirements:

• I have created tests for my code changes, and the tests are passing.
• I have executed the pre-commit hooks locally.
• I have updated the documentation accordingly.
• The commit message follows our guidelines: https://github.com/konstellation-io/kdl-server/blob/main/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• My change requires a change to the documentation (create a new issue if the documentation has not been updated).

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

MinIO credentials are lost when CR template updates.

Closes #

What is the new behavior?

MinIO credentials are propagated when CR template updates.

Does this PR introduce a breaking change?

• Yes
• No

Now, CRD and CR require extra field specs.inputData

Other information